Skip to content

Drop the paratest conflict pin and require pest ^5.3.4 - #14

Merged
jayjfletcher merged 1 commit into
mainfrom
ring-master/drop-paratest-conflict-pin
Oct 28, 2026
Merged

jayjfletcher merged 1 commit into
mainfrom
ring-master/drop-paratest-conflict-pin

Conversation

@jayjfletcher

Copy link
Copy Markdown
Member

Summary

  • Removes the temporary conflict on brianium/paratest >=7.26.1. Pest 5.3.4 requires paratest ^7.27.4, so the conflict now stops composer from resolving.
  • Requires pestphp/pest ^5.3.4.

Closes #13.

CI goes red until the matching PennantPlus PR is merged. Cortex and PennantPlus each require the other's dev-main in their dev dependencies, so neither can resolve while the other still has the pin. Merge both, then re-run CI on whichever was merged first.

Test plan

  • Installed against PennantPlus's pin-drop branch: pest 5.3.4 with paratest 7.27.4
  • vendor/bin/pest --parallel passes (Cortex: 656 tests, PennantPlus: 124)
  • CI green once both PRs are merged

🤖 Generated with Claude Code

Pest 5.3.4 requires paratest ^7.27.4, so the temporary conflict on
brianium/paratest >=7.26.1 now stops composer from resolving.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@jayjfletcher
jayjfletcher merged commit c914866 into main Oct 28, 2026
0 of 4 checks passed
@jayjfletcher
jayjfletcher deleted the ring-master/drop-paratest-conflict-pin branch October 28, 2026 05:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fix CI failure on setup-php 2.40.0 bump (PR #8)

1 participant